Problem Note 40563: The SAS Marketing Automation Launcher returns an error after running a scheduled flow even though the flow completes normally
The SAS Marketing Automation Launcher might return an error code of 90 at the end of a scheduled campaign or diagram. However, the error does not affect the successful execution of the campaign or diagram and it does not appear in the SASMarketingAutomationCorerelease.log file. However, the sasmalauncher log does contain the following error when this problem occurs:
com.sas.analytics.crm.ma.launcher.LaunchException: 90 ...
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.logoff(ExecutionFacade.java:246)
at com.sas.analytics.crm.ma.launcher.ExecutionFacade.execute(ExecutionFacade.java:102)
at com.sas.analytics.crm.ma.launcher.MALauncher.launch(MALauncher.java:563)
at com.sas.analytics.crm.ma.launcher.MALauncher.main(MALauncher.java:184)
Caused by: com.sas.analytics.crm.error.client.UserException: session,
id=513b23d727e57b06:47745907:12a32c27ecf:-316d
at com.sas.analytics.crm.security.ejb.MASessionCache.getSession(MASessionCache.java:442)
at com.sas.analytics.crm.security.ejb.MASessionCache.removeSession(MASessionCache.java:374)
at com.sas.analytics.crm.security.ejb.MASessionCache.decrementCounter(MASessionCache.java:828)
at com.sas.analytics.crm.security.ejb.MASessionHelper.decrementCounter(MASessionHelper.java:133)
at com.sas.analytics.crm.security.ejb.SecurityManagerBean.logout(SecurityManagerBean.java:599)
at com.sas.analytics.crm.security.ejb.client.EJSRemoteStatelessSecurityManagerBean_41c23772.logout
(Unknown Source)
at com.sas.analytics.crm.security.ejb.client._SecurityManager_Stub.logout(_SecurityManager_Stub.java:627)
at sun.reflect.GeneratedMethodAccessor1299.invoke(Unknown Source) ...
The error also appears in the web application server log for which SAS Marketing Automation Core is installed, as shown in this example from WebSphere:
RemoteInvocat I org.springframework.remoting.support.RemoteInvocationTraceInterceptor invoke
Processing of HttpInvokerServiceExporter remote call resulted in exception: com.sas.analytics.crm.security.client.
SecurityManagerInterface.logout com.sas.analytics.crm.error.client.UserException: session,
id=513b23d727e57b06:47745907:12a32c27ecf:-316d
at com.sas.analytics.crm.security.ejb.MASessionCache.getSession(MASessionCache.java:442)
at com.sas.analytics.crm.security.ejb.MASessionCache.removeSession(MASessionCache.java:374)
at com.sas.analytics.crm.security.ejb.MASessionCache.decrementCounter(MASessionCache.java:828)
at com.sas.analytics.crm.security.ejb.MASessionHelper.decrementCounter(MASessionHelper.java:133)
at com.sas.analytics.crm.security.ejb.SecurityManagerBean.logout(SecurityManagerBean.java:599)
at com.sas.analytics.crm.security.ejb.client.EJSRemoteStatelessSecurityManagerBean_41c23772.logout
(Unknown Source)
at com.sas.analytics.crm.security.ejb.client._SecurityManager_Stub.logout(_SecurityManager_Stub.java:627)
at sun.reflect.GeneratedMethodAccessor1299.invoke(Unknown Source) ...
This problem is caused by a synchronization error. This error occurs when SAS Marketing Automation finishes running a scheduled campaign or diagram and then releases the session that was used to run that campaign or diagram. The error does not affect successful execution of the campaign or diagram. You can ignore the error.
Operating System and Release Information
| SAS System | SAS Marketing Automation | Linux | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| HP-UX IPF | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| 64-bit Enabled Solaris | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| 64-bit Enabled HP-UX | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| 64-bit Enabled AIX | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Windows Vista for x64 | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Windows Vista | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows XP Professional | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows Server 2008 for x64 | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 for x64 | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Standard Edition | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise Edition | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Datacenter Edition | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows XP 64-bit Edition | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Enterprise 64-bit Edition | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft Windows Server 2003 Datacenter 64-bit Edition | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 5.3 | 5.4 | 9.2 TS2M0 | 9.2 TS2M0 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | low |
| Date Modified: | 2012-01-11 17:18:53 |
| Date Created: | 2010-08-11 14:12:07 |
